Managing Versions

Versions allow a series of changes to be applied to the workflow container as of a certain date. These changes will remain in effect until the next version date arrives, at which point the settings for that version will be applied.

Each version can introduce overrides for features such as formulas, data tables, and behavior settings for fields.

  1. Open the appropriate Workflow Container. For instructions on finding and opening a container, see the section on Managing Workflow Containers.
  2. In the Workflow Container Menu widget, select Versions. The Workflow Container Versions page opens with a list of all versions of the current container.
  3. If there are a large number of versions, see the Using Grids section for help on finding the appropriate versions.

  4. Select an action.
    • Click a link in the Name column to view an existing version.
    • Click Add to add a new version.
  5. On viewing or creating a version, the Workflow Container Version page opens.
  6. The panels and fields are described below.  Fields marked with a red asterisk * are required.
  7. Name

    Enter the name of the version.  This is the configuration name, and does not appear in the workflow itself.

    Description

    A description can be provided for the version.  This information is only displayed here and in the Workflow Container Versions list.

    Effective Date

    Enter a date for when this version comes into effect.  The date can be entered manually or selected from the calendar lookup .

    Activation Criteria Optionally select a Trigger that, when evaluates to True, sets the current system date as the Effective Date for the Version.
    Formula Overrides

    This link is available once the version has been saved. Click this link to open the Formula Overrides list for the current version. See the Managing Formula Overrides section for details.

    Data Table Overrides

    This link is available once the version has been saved. Click this link to open the Data Tables page to manage overrides for the current version. See the Managing Data Table Overrides section for details.

    Behavior Overrides

    This link is available once the version has been saved. Click this link to open the Behavior Overrides page to manage overrides for the current version. See the Managing Behavior Overrides section for details.

  8. Select an action.
    • Click Save to save the version but remain on the page.
    • Click Save & Close to save the version and return to the versions list.
    • Click Close to return to the versions list without saving the version.

Managing Formula Overrides

Formula overrides allow a new formula to be substituted into a calculated field without altering the core field itself.

  1. Open the appropriate Workflow Container. For instructions on finding and opening a container, see the section on Managing Workflow Containers.
  2. Open the appropriate Container Version. For instructions on finding and opening a container version, see the section on Managing Versions.
  3. Click the Formula Overrides link. The Formula Overrides page opens with a list of all overrides configured for the current version.
  4. Some columns have been hidden.

    If there are a large number of overrides, see the Using Grids section for help on finding the appropriate overrides.

  5. Select an action.
    • Click a link in the Field column to navigate to the Field Management page, where the formula can be edited directly within the Calculated Field Formula field. From this page it is possible to publish the single field formula, making it quickly available for testing or to be used immediately without publishing the rest of the workflow. For additional information, see the Publishing a Calculated Field's Formula section.
    • Click a link in the Formula column to view or modify an existing override. Proceed to step 7 below.
    • Click Add to add a new override.
    • Check the boxes for one or more overrides and click Delete to remove the selected overrides from the version.
    • Click Close to return to the Workflow Container Version page.
  6. On creating an override, the Available Formulas window opens.
  7. The Available Formulas panel lists the available calculated fields in the workflow container, not including those that already have overrides in the current version.

  8. Click a link in the Formula column to create an override for that field, or click Close to close the window.
  9. On clicking a link in the Formula column, the Formula window opens.
  10. Original Formula

    This field displays the original formula from the field. This is the formula from the core workflow container, and does not reflect any other version overrides that may be in effect. To view a large formula, click the Full Screen icon.

    Override Formula

    Enter the new formula. To edit a large formula, click the Full Screen icon.

  11. Select an action.
    • Click Save to save the override but remain on the page.
    • Click Save & Close to save the override and close the window.
    • Click Close to close the window without saving the override.

Managing Data Table Overrides

Data table overrides allows new data table instances to be substituted into a data table without altering the core settings of the table itself.

  1. Open the appropriate Workflow Container. For instructions on finding and opening a container, see the section on Managing Workflow Containers.
  2. Open the appropriate Container Version. For instructions on finding and opening a container version, see the section on Managing Versions.
  3. Click the Data Table Overrides link. The Data Tables page opens with a list of all data tables in the current workflow container.
  4. Some columns have been hidden.

    If there are a large number of data tables, see the Using Grids section for help on finding the appropriate tables.

  5. Select an action.
    • Click a link in the Name column to manage the overrides for that table.
    • Click Close to return to the Workflow Container Version page.
  6. On opening a table, the Data Table Management page opens. Additional information on the data table is included in the page header.
  7. The panels and fields are described below.
  8. Name

    Displays the name of the table.

    Code

    Displays the internal reference code.

    Key Columns

    Displays the selected key columns.

    Sorting Column

    Displays the selected sorting column.

    The Columns grid displays all columns included in the table, and the sequence as they appear in the source file.

    Some columns have been hidden.

    The Data Table Instances panel lists all instances included in this version of the data table, and is used to manage the instances. See the next step for instructions.

    Created By

    Identifies the date and time the data table was created, and the user who created it. This is the information from the original data table, and not the override version.

    Last Modified By

    Identifies the last date and time the data table was changed, and the user who made the changes. This does not include changes to data table instances or version overrides.

  9. The Data Table Instances panel is used to add and manage the table data that will be available when this version of the container is in effect.
  10. Some columns have been hidden.

    1. Select an action.
      • Click a link in the Data Table Instance Name column to view an existing instance.
      • Click a link in the File Name column to view the original uploaded Excel file.
      • Click a link in the Download column to download the data from that instance into a new Excel file.
      • Click Add to add a new instance.
      • Check the boxes for one or more instances and click Delete to remove the selected instances and all associated data.
    2. On viewing or creating an instance, the Domain / Rate Table Management window opens.
    3. The panels and fields are described below.  Fields marked with a red asterisk * are required.
    4. Data Table Displays the name of the current data table. This field cannot be modified.
      Name Enter the name of the data table instance.
      Code This is an internal reference code that must be unique.  A code can be entered manually, or leave the field blank to have the system generate a code on saving. 
      Culture An instance can be associated to a language, including a regional dialect. If no selection has been made, the data will not be culture-specific.  When the data table is accessed, the system will use the appropriate instance for the browser’s language settings.
      Effective Date A date can be specified for when this instance comes into effect.  The date can be entered manually or selected from the calendar lookup .  When the data table is accessed, the system will use the most recently uploaded table that corresponds to a specific date.
        Dates can be defined outside of the period for the current version, but will have no effect outside of the version period. If the effective date of the override instance is before the effective date of the version, the override instance will only take effect when the version becomes effective. If another version comes into effect before an override instance takes effect, then that override will not be applied.
        If multiple versions begin on the same date and all other criteria match, the most recently created version will be used.
      Imported File Name Once a file has been uploaded, this field will display the file name.
      Select File to Import Click the button in the field to open a standard file browser window.  Locate and select the appropriate file, and the file name and path appear in the field.

      Note:  

      Culture and Effective Date are used to define which instance will be used when the data table is accessed.

      • Instances are only valid on or after their effective date, and only within the effective period of the version.  The system will identify all instances valid on the specified date.   
      • Of the valid tables, the system will then check Culture settings for an exact match on both language and region.  If no match is found, the system will then check for a match on just language.  If no match on language alone is found, the system will then check for instances where no Culture is selected.
      • If multiple instances are valid on both Effective Date and Culture, the system will use the one most recently uploaded.
      • If no valid instances are found, the system will not return any result.

      The columns and column labels in the uploaded file must match the sample file uploaded to the selected Data Table.  If not, the file upload will be rejected and an error will be displayed.

      The Status panel becomes available once the current data table instance has been saved.

      Created By

      Identifies the date and time the instance was created, and the user who created it.

      Last Modified By

      Identifies the last date and time the instance was changed, and the user who made the changes.

    5. Select an action.
      • Click Save to save the instance and keep the window open. When saving, any file chosen to be uploaded will be automatically imported.
      • Click Close to close the window without saving the instance.
  11. In the Data Table Management page, click Close to return to the Data Tables list.

Managing Behavior Overrides

Behavior overrides allow new behavior rules to be applied to a field without altering the core field configuration.

  1. Open the appropriate Workflow Container. For instructions on finding and opening a container, see the section on Managing Workflow Containers.
  2. Open the appropriate Container Version. For instructions on finding and opening a container version, see the section on Managing Versions.
  3. Click the Behavior Overrides link. The Behavior Overrides page opens with a list of all overrides configured for the current version.
  4. Some columns have been hidden.

    If there are a large number of overrides, see the Using Grids section for help on finding the appropriate overrides.

  5. Select an action.
    • Click a link in the Field column to view an existing override.
    • Click Add to add a new override.
    • Check the boxes for one or more overrides and click Delete to remove the selected overrides from the version.
    • Click Close to return to the Workflow Container Version page.
  6. On viewing or creating an override, the Field Behavior Override page opens.
  7. The panels and fields are described below.  Fields marked with a red asterisk * are required.
  8. Select the panel or grid containing the field for the override. The rest of the configuration options will be displayed.

    Note that the panel or grid cannot be changed once selected. To choose a different panel or grid, Close the override and Add a new one.

    Select the fields where the rule applies.  If any fields are added to the panel that should be included in an existing rule, the rule must be edited to select the new fields.

    Select how the field should behave under the defined circumstances.  For each option select Yes to apply the behavior or No to not apply it.

    Required

    The field must be completed before the user can save the screen.

    Hidden

    The field is not shown in the form.

    Read-Only

    The field can be viewed, but cannot be edited.

    The Trigger field is used to assign a trigger to the rule.  The rule is only applied if the trigger evaluates as true.

    Note: Use caution when creating override rules for fields that are used in triggers. It can create circumstances where users activate changes in a form and are unable to undo the changes.

    When a user makes changes in a screen that activates an override rule, it does not occur immediately.  The rule is applied when any action is taken that saves and refreshes the screen.

    If a field is changed to hidden by an override rule, it retains its current value.

    Select the types of transaction where the rule applies.

    New Business

    The original version of a transaction or policy.

    Endorsement

    A modification to a bound policy.

    Adjustment

    An adjustment to a bound policy.

    Declaration

    A periodical modification to a bound policy.

    Renewal

    A renewal for an expired policy.

    Cancellation

    A cancelled policy.

    Reinstatement

    A policy that was reinstated after being cancelled.

    Select the transaction or policy statuses where the rule applies.

    Incomplete

    A transaction that has not yet had a quote calculated.

    Underwriting Required

    A transaction that does not meet the requirements of the master cover and must either be corrected or submitted to the insurance representatives for review.

    Quoted

    A transaction that has been quoted and is ready to be bound.

    Referred

    A transaction that does not meet the requirements of the master cover and has been submitted to the insurance representatives for review.

    Bound

    A policy that has been bound.

    Rescinded A cancellation transaction that has been rescinded.

    Declined

    A transaction that went into quote request or referral, but has been declined.

    Lost

    A quoted transaction that has been marked as lost business.

    Select the types of user where the rule applies.  The user viewing the screen must have one or more of the selected security roles in order for the rule to be applied.

    Note: At least one option must be selected in each category.  For a rule to apply to all options in a category, all options must be selected.

  9. Select an action.
    • When creating a new override, click Save & New to save the override and clear the form to add additional overrides.
    • When viewing an existing override, click Save to save the override and remain on the page.
    • Click Save & Close to save the override and return to the overrides list.
    • Click Close to return to the overrides list without saving the override.